-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add reverse proxy step to onboarding for feature flags #20906
Conversation
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
Size Change: +52 B (0%) Total Size: 821 kB ℹ️ View Unchanged
|
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌
…to onboarding-proxy-step
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
810b0ea
to
e724cd5
Compare
Here is the A/B test: https://us.posthog.com/project/2/experiments/24377. |
Problem
A reverse proxy allows users to send events to PostHog Cloud using your own domain. This means that events are sent from their own domain and are less likely to be intercepted by tracking blockers.
Product like feature flags require a proxy in order to make sure the necessary requests succeed for all users.
Changes
We already have the documentation for how to set up a proxy. This PR is adding the a step to the onboarding flow to let the user know they should set one up.
Few notes:
Other items discussed while doing this: